Methods for providing notifications for follow-up actions in response to events detected by an automation system, and systems and devices related thereto

ABSTRACT

An automation system may include a control panel monitoring one more automation system components. When an event is detected at an automation system component, the control panel may automatically access a local or remote data source and identify procedures to be implemented in response to the event. The procedures may include follow-up actions and procedures specific to a particular dealer of the automation system. Dealer-specific procedures may then be displayed or otherwise communicated by the control panel to alert the user of what actions to take or to expect.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/206,490, filed Mar. 12, 2014, titled “METHODS FOR PROVIDINGNOTIFICATIONS FOR FOLLOW-UP ACTIONS IN RESPONSE TO EVENTS DETECTED BY ANAUTOMATION SYSTEM, AND SYSTEMS AND DEVICES RELATED THERETO,” whichclaims the benefit of U.S. Provisional Patent Application No. 61/791,077titled “METHODS FOR PROVIDING NOTIFICATIONS FOR FOLLOW-UP ACTIONS INRESPONSE TO EVENTS DETECTED BY AN AUTOMATION SYSTEM, AND SYSTEMS ANDDEVICES RELATED THERETO” filed on Mar. 15, 2013, which is assigned tothe assignee hereof, the disclosures of which are expressly incorporatedherein in their entireties by this reference.

TECHNICAL FIELD

The present disclosure relates to automation systems. More particularly,embodiments of the present disclosure relate to the use of an automationsystem with a building and responding to events associated with theautomation system. More particularly still, embodiments of the presentdisclosure relate to providing users of automation systems withcustomized information and options based on the specific procedures of adealer or provider of the automation system.

BACKGROUND

People are increasingly interested in providing security and securityservices to various locations, buildings, etc. Security in a homesetting, for example, may be particularly significant for a home owneror resident who is away from home, who has small children, or who keepsvaluable items at the home. For such an owner or resident to feelsecure, security and privacy may be provided through various securitymechanisms. Example mechanisms and methods include using door and windowlocks, the use of video security cameras, or intrusion detectionsecurity systems. Some or all of these components may be automated, andpotentially included as part of an automation system associated with oneor more other functions.

In an automation system, various types of alerts or events may betriggered. For instance, in the context of a security system, an alertmay be triggered if a window or door lock detects a breach. Opening of adoor or window once armed may indicate that an intruder potentiallygained access to the building. Other similarly significant, or morebenign, alerts may also be triggered. By way of illustration, a wirelesssensor may lose power or otherwise stop communicating with the securitysystem. In such a case, an alert may be created to indicate thatcommunication has stopped. Other alerts and events may of course bedetected, and may be associated with a wide variety of systems,including security systems, sprinkler systems, entertainment systems,lighting systems, and the like.

Generally, when an event or alert is identified, the user may benotified. As an example, a home automation control panel may displaytext or other indicia to indicate what event has occurred. In the aboveexamples, for instance, the control panel may indicate that an entry hasbeen breached or that the control panel has lost communication with acontrol panel. The user may then take appropriate actions to try andremedy the event. For instance, the user may call a dealer or providerof the automation system to schedule a maintenance service to determinewhy the sensor has lost communication, or the user may call the policeif it is suspected an intruder has entered, or attempted to enter, thebuilding.

SUMMARY

In accordance with aspects of the present disclosure, embodiments ofmethods, systems, software, control panels, computer-readable media, andthe like are described that relate to security systems and other typesof automation systems. In accordance with some embodiments of thepresent disclosure, a control panel is connected to one or moreautomation components of an automation system, and monitors eventswithin the automaton system. Upon detection of an event, the controlpanel may automatically access information about specific proceduresset-up by a dealer of the automation system. The specific procedures maybe displayed or otherwise communicated by the control panel to allow auser to be aware of what actions the user should take and/or whatactions the dealer or another party will take. In some embodiments, theprocedures relate to out-of-band follow-up procedures.

In a more particular example embodiment, an automation system may detectand event. The control panel may access a local or remote data store toidentify the event, a procedure specific to the event, and the dealerassociated with the automation system. Some procedures may occur in-bandand potentially happen automatically, such as sounding an alarm,contacting emergency personnel, or the like. Other procedures may beout-of-band or delayed. As an example, a phone call to check on acustomer, or scheduling of a service call may be scheduled to occur at alater time. Any of these procedures may not only be implemented, butalso communicated to the control panel and displayed or otherwise outputto let a user know what actions—whether occurring now or later—are partof the dealer's service and system.

According to another embodiment of the present disclosure, event anddealer-specific actions may be facilitated by a control panel. Specificprocedures for an event and dealer may include information about controlpanel options or functions to be enabled. Example functions may includecommunication functions enabled in response to an event, schedulingfunctions in response to an event, and instructional functions inresponse to an event. Different dealers may set-up different functionsand procedures such that the same event at different control panels mayresult in the display and/or use of different procedures or functions.

Other embodiments of the present disclosure relate to registering eventand dealer-specific events in a procedure description system. Access maybe granted to the procedure description system, and a particular dealermay be identified. Specific procedures associated with the dealer maythen be registered. To register a procedure, an event may be specified,along with an automatic, delayed, in-band, out-of-band, or otherprocedure. Control panel or other automated functions associated with anevent may also be specified. A storage device may then store informationabout such procedures and/or functions, and associate them withparticular events and/or automation system dealers. The storage devicemay include information for only a single dealer, or may includeinformation for multiple dealers.

Other aspects, as well as the features and advantages of variousaspects, of the present disclosure will become apparent to those ofordinary skill in the art through consideration of the ensuingdescription, the accompanying drawings and the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which features and other aspects ofthe present disclosure can be obtained, a more particular description ofcertain subject matter will be rendered by reference to specificembodiments which are illustrated in the appended drawings.Understanding that these drawings depict only typical embodiments andare not therefore to be considered to be limiting in scope, nor drawn toscale for all embodiments, various embodiments will be described andexplained with additional specificity and detail through the use of theaccompanying drawings in which:

FIG. 1 is a schematic illustration of an example automation systemaccording to one embodiment of the present disclosure;

FIG. 2 is a schematic illustration of an example control panel usable inan automation system, according to one embodiment of the presentdisclosure;

FIG. 3 illustrates an example method for providing an automation systemuser with custom procedures in response to an event of the automationsystem, according to another embodiment of the present disclosure;

FIG. 4 illustrates an example method for a dealer or provider ofautomation services to register custom procedures to be used withcustomers or users, according to an embodiment of the presentdisclosure;

FIG. 5 depicts a table illustrative of an example data store for storingcustom procedures for any of a number of different dealers or providersof automation services, according to another embodiment of the presentdisclosure;

FIGS. 6-8 illustrate an example control panel usable in detecting anevent and displaying information based on procedures customized for adealer or provider of automation services, according to an embodiment ofthe present disclosure;

FIG. 9 illustrates an example control panel usable in coordinatingspecific action in response to an event and custom procedures of thecontrol panel of FIGS. 6-8;

FIGS. 10 and 11 illustrate another example control panel usable indetecting an event and displaying information based on procedurescustomized for a dealer or provider of automation services, according toan embodiment of the present disclosure;

FIGS. 12-14 an example control panel usable in coordinating specificactions in response to an event, and based on custom procedures of adealer or provider, using the control panel of FIGS. 10 and 11; and

FIGS. 15-16 illustrate example flow diagrams of methods for providing anautomation system user with custom procedures in response to an event ofthe automation system, according to embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Systems, devices and methods of the present disclosure are configuredfor use in connection with residential and/or commercial buildings, orwith other locations which may use an automation system. Withoutlimiting the scope of the present disclosure, a home or business mayhave a security system installed to monitor use of the building,including entry into the building through a door, window, or othersimilar entry point. Sensors at the entry point may detect when theentry point is open or closed, and can respond in different ways inresponse to a change in status. For instance, when the security systemis armed, an alarm may sound when the door is opened. Optionally, thepolice or security may be contacted to have them monitor the building.Of course, other types of components within the automation system mayresult in other responses. For instance, if a leak in a sprinkler systemis detected, a response may include shutting off a valve. If no one isdetected in a particular location, lighting may be turned off or dimmed.

Turning now to FIG. 1, an example distributed system 100 is illustratedfor allowing control and/or monitoring of certain aspects of a physicallocation (e.g., a building such as a home, residence, office, etc., anoutdoor space, and so on). The illustrated distributed system 100 maygenerally represent, or include, an automation system associated withthe particular location. As part of such a distributed system 100, acontrol panel 102 a may be used. The control panel 102 a may, but neednot necessarily, be located at the location being monitored orcontrolled. Certain aspects of the distributed system 100, or theautomation system, may be administered through the control panel 102 a,or a user may be provided with information about a status of theautomation system.

More particularly, the illustrated distributed system 100 may includethe control panel 102 a, which can interact with an automation system104 a for the location. The automation system 104 a may generally bereferred to herein as a “security system,” but need not be limited tosecurity-related features. Indeed, the automation system 104 a of theillustrated embodiment may include a number of different components, anyor all of which may be used in connection with the control panel 102 a.In this particular embodiment, for instance, the automation system 104 aincludes a communications system 106, an entertainment system 108, aheating, ventilation, and air conditioning (“HVAC”) system 110, alighting system 112, a security system 114, a sprinkler system 116, anda telephone system 118.

Any or all of the systems 106-118 may include sensors, controllers,valves, switches, or other components, or any combination thereof, thatcan be controlled by the control panel 102 a, or which can have a statusmonitored by the control panel 102 a. Such components, which aregenerally used to monitor or control some aspect of a physical locationassociated with the control panel 102 a, may generally be referred toherein as “automation components.” and can perform a variety offunctions. For instance, a set of one or more automation components maybe integrated as part of the security system 114 associated with thelocation. In some embodiments, the automation components of the securitysystem 114 may include sensors that detect intruders (e.g., unauthorizedopening of a door or window, motion sensors, etc.), sensors that detectsmoke or fire, or some other security-related component or a combinationthereof. In some embodiments, the security system 114 may includeautomation components such as cameras which obtain still or video imagesof a location.

Automation components of the automation system 104 a may take any numberof forms, and are not limited to security components. For instance,automation components may include entertainment components such astelevisions, recordable media players (e.g., DVD player, Blu-Ray Player,digital video recorders, VCR, set-top box, etc.), projectors, speakers,stereos, and the like, any or all of which may be separate from thecontrol panel. Such entertainment components may be used, by way ofexample only, to turn on a television, radio, optical disk player, orthe like, change a channel or volume of television or radio, or forother purposes. In the same or other embodiments, automation componentsmay include thermostats, air conditioners, furnaces, temperaturesensors, and the like, or controllers therefor. Monitored and/orcontrollable automation components may further include lighting systemcomponents such as light fixtures, switches, motion sensors, etc. tomonitor the status of lights and/or to turn lights on or off. Additionalcomponents or controllers may include security system componentsincluding sensors or detectors (e.g., motion sensors, magnetic sensors,intrusion sensors, vibration sensors, infrared sensors, ultrasonicdetectors, microwave detectors, contact sensors, photoelectric beamdetectors, smoke detectors, temperature sensors, carbon monoxidedetectors, etc.), video or still cameras, speakers, microphones, orother components. In embodiments where the automation system 104 aincludes a sprinkler system 116, the automation components may includevalves, actuators, sensors (e.g., flow rate sensors, proximity sensors,etc.), sprinklers, pumps, and the like. In a similar manner, where oneor more of the automation components is part of a telephone system 118,the automation components may include telephones, answering machines,call forwarding components, intercoms, and the like. Some or all of theautomation components of the various systems 106-118 may also includewireless communication system components. As an example, the automationcomponents may include routers, switches, access points, repeaters,bridges, and the like.

When a given condition occurs at a monitored automation component, thecontrol panel 102 a may be used to cause other automation components torespond. Additionally, or alternatively, the control panel 102 a maycommunicate with components, including those remote from the physicallocation. As an example, upon monitoring the automation components ofthe systems 106-118, the control panel 102 a can detect changes instatus, which changes may correspond to events. For instance, asdiscussed herein, if the security system 114 includes an automationcomponent, such as a sensor, at a door, the control panel 102 a candetect when the door is opened. If the security system 114 is armed,opening of the door may correspond to an event indicating a potentialintruder has entered the building. The control panel 102 a may beprogrammed to respond accordingly. For instance, the security system 114may also include an alarm automation component. The control panel 102 amay turn on the alarm of the alarm automation component. Of course, thecontrol panel 102 a may also perform other actions, including initiatinga phone call to the police or security (e.g., using the telephone system118). As will be apparent in view of the disclosure herein, in the eventof another type of event—whether detected using the security system 114or another of the systems 106-118—the control panel 102 a can facilitatetaking of other actions.

In at least some embodiments, the control panel 102 a may communicatewith one or more third parties. For instance, FIG. 1 illustrates thecontrol panel 102 a as being in communication with a network operationscenter (“NOC”) 120. Optionally, the control panel 102 a may provide theNOC 120 with information about detected events. In some cases, the NOC120 may then take one or more actions. By way of illustration, if thecontrol panel 102 a notifies the NOC 120 that a potential intruder hasentered a building, the NOC 120 may respond by notifying police orsecurity. Consequently, some actions taken in response to a detectedevent may be taken by the NOC 120 rather than by the control panel 102a.

To allow the NOC 120 to be aware of detected events, and to potentiallyrespond to such events, the control panel 102 a may communicate with theNOC 120 through a communications network 122. The communications network122, which may carry electronic communications, may include theInternet, local area networks, wide area networks, virtual privatenetworks (“VPN”), telephone networks, other communication networks orchannels, or any combination of the forgoing. Thus, it should beunderstood that the communications network 122 may operate in any numberof different manners, and can include different components, and may bedistributed so as to include different components at differentlocations. For instance, the communications network 122 may include awireless communication system such as that provided by a mobile phoneprovider. As an example, the control panel 102 a may include a radiocomponent to communicate with or using the communications network 122through GSM, CDMA, LTE, HSPA+ or other similar technologies used bymobile phone systems. In other embodiments, other wireless systems oreven wired communication may be used. Any combination of the foregoingmay also be used. Thus, while a single communications network 122 isillustrated, such a component may be illustrative of multiple devices orcomponents. For instance, the communications network 122 may includemultiple networks interconnected to facilitate communication.

Regardless of the particular type of protocols and systems used by thecommunications network 122, the NOC 120 may receive information from thecontrol panel 102 a about events detected using automation components.In some embodiments, the NOC 120 includes human operators who monitorthe events. Based on the type of event detected, the human operator mayinitiate some type of response. That response may be implemented usingthe control panel 102 a by, for instance, sending information back tothe control panel 102 a, initiating voice communication through thecontrol panel 102 a, or in other manners. When implementing actionsusing the control panel 102 a, the actions may be considered to be“in-band”. In other embodiments, the human operator may initiate an“out-of-band” response. Such a response may include actions takenwithout use of the control panel 102 a. For instance, after detecting anintruder, a phone call may be made to police or security to request thatthey monitor the location where the intruder was detected. A phone callcould also be placed to the user or owner of the automation system 104a. As an example, the NOC 120 may be used to place a call to a telephone124, send an email retrieved at the computing device 126, or otherwiseinitiate some communication or action.

While some responses may be taken or initiated by using a humanoperator, other responses may be automated. For instance, if a signalrepresentative of a potential intruder alert is detected, the NOC 120may automatically initiate an action, such as calling or otherwisecommunicating with the police, a home owner, or the like (e.g., textmessage, e-mail, emergency alert systems, etc.). The NOC 120 may includecomputing devices to initiate such actions. In accordance with at leastone embodiment, the NOC 120 includes, or communicates with, a data store127. The data store 127 may include information to allow automatedcomponents of the NOC 120 to determine what actions to take. Each eventmay, for instance, be associated with a different in-band and/orout-of-band action that can be taken, with such different actions beingstored in the data store 127. As discussed in greater detail herein, thedata store 127 may also store a description of dealer-specificprocedures, including follow-up procedures, as part of a proceduredescription system.

The NOC 120 may optionally be used for other or additional purposesbeyond responding to events detected by the automation system 104 a. Forinstance, the NOC 120 may be a central monitoring location for use withmultiple control panels 102 a-102 c. Indeed, the NOC 120 may be used tomonitor any number of control panels 102 a-102 c, each of which may beconnected to its own automation system 104 a-104 c. Further, the NOC 120may update software or firmware on the control panels 102 a-102 c toensure that the control panels 102 a-102 c are operating andcommunicating properly with automation components of their respectiveautomation systems 104 a-104 c and/or with the NOC 120. As a result ofsuch monitoring, when the automation components of an automation system104 a-104 c detect a certain event (e.g., a security-related event suchas a break-in, a fire, etc.), the control panel 102 a-102 c can obtainthe information and optionally takes some prescribed action (e.g.,initiating an alarm, performing a corrective action, notifying anadministrator or user, etc.). The corresponding control panel 102 a-102c may also communicate such information to the NOC 120 through thecommunication network 122 for review or action.

The distributed system 100 of the present disclosure may be implementedas a communication system in which the operations of various systems andcomponents can be monitored through communication links. As discussedherein, such communication links may include wired or wireless links, orcan include a combination of wired and wireless links, any or all ofwhich may use different protocols or networks. Regardless of theparticular mode of communication, the status or operation of devices andcomponents can be reported to, or controlled using, the correspondingcontrol panel 102 a, network operations center 120, or even otherelectronic devices 124, 126. The control panel 102 a, and the componentsof the automation system 104 a, may therefore include a number ofdifferent types of components that provide or receive electronic signalsof one or more different types.

By way of example, the control panel 102 a may be equipped to use one ormore different communication protocols in communicating with automationcomponents of the automation system 104 a and with the communicationnetwork 122. Such communication protocols may be implemented using anycombination of one or more of wired or wireless communication. As anexample, automation components of the automation system 104 a mayoperate using a wireless protocol, or system that allows a mesh networkto be formed. Each automation component may, for instance, optionally beable to communicate with some or any other automation component,provided they are in range of each other. If the automation componentsuse a wireless system for communicating with the control panel 102 a, anautomation component that is in range of the control panel 102 a mayalso send information to, or receive information from, the control panel102 a. In some embodiments, the automation components may communicatewith each other and the control panel 102 a using the same communicationprotocol. Although not intended to limit the scope of the presentdisclosure, an example communication protocol for such an embodiment maybe a low power, short range wireless communication protocol (e.g.,Z-Wave, ZigBee, etc.). In other embodiments, larger range wirelesscommunication protocols (e.g., WiFi, LightwaveRF, etc.) may be used inaddition to, or instead of, the shorter range alternatives. Suchconnections may also allow two-way communication or may provide onlyone-way communication.

The control panel 102 a may also optionally communicate with thecommunication network 122 and/or the NOC 120 or electronic devices 124,126 using the same or other protocols. As an example, if the electronicdevice 124 is sufficiently close to the control panel 102 a, a physicalconnection may be used, or a suitable wireless communication protocol(e.g., Z-Wave, ZigBee, Bluetooth, WiFi, etc.) may be used.

Communication with the communication network 122 may also be made in anysuitable manner, including using wireless or wired communication, or acombination thereof. For instance, as discussed herein, an examplecontrol panel 102 a may communicate with a network 122 operating on amobile telephone system. A GSM, CDMA, LTE, HSPA+, or other similarwireless communication component may therefore be included in thecontrol panel 102 a and the network 122 to allow for such communication.In other embodiments, the network 122 may have other forms to allow foralternative or additional types of communication between the network 122and the control panel 102 a. Moreover, a NOC 120 may communicate withdifferent control panels 102 a-102 c of different automation systems 104a-104 c using the same or different communication protocols, andpotentially allow such control panels 102 a-102 c to communicate witheach other.

Turning now to FIG. 2, an example control panel 200 is schematicallyillustrated. It should be appreciated in view of the disclosure hereinthat the control panel 200 may be used in the distributed system of FIG.1 or in connection with any other system. Further, the illustratedcontrol panel 200 is merely illustrative, and a control panel of thepresent disclosure may have fewer or additional components, or elementsother than those expressly described or illustrated, or may be used inconnection with systems or components other than those of FIG. 1 or themethods, systems, and devices disclosed herein.

In FIG. 2, the control panel 200 includes multiple componentsinteracting together over one or more communication channels. In thisembodiment, for instance, one or more processors 228 may communicatewith input/output devices 230, a communication interface 232, memory 234and/or a mass storage device 236 via a communication bus 238. Theprocessors 228 may generally include one or more processing components,including a central processing unit, a graphics processing unit, or thelike, any of which may be capable of executing computer-executableinstructions received or stored by the control panel 200.

The processors 228 may communicate with the communication interface 232using the communication bus 238. The communication interface 232 mayreceive or send communications via one or more networks (e.g., network122 of FIG. 1) or otherwise communicate with other components or devices(e.g., automation system 104 a of FIG. 1). Received communications maybe provided over the communication bus 238 and processed by theprocessors 228.

In the particular embodiment illustrated in FIG. 2, the communicationinterface 232 may include multiple components to allow communication viaone or more different protocols. For instance, the illustratedembodiment includes an interface component 240 for connecting to localcomponents, such as over a wireless mesh network. As discussed herein,an example of the component 240 may include radio which operates usingZ-Wave, ZigBee, or other protocols, or some combination thereof. Such acomponent may specifically be used to communicate with security or otherautomation or automation system components for a residence or otherstructure, including one or more sensors, cameras, controllers, and thelike.

In still another example embodiment, an example communication interface232 may include an interface component 242 for communicating over amobile telephone network. An example network may include, for instance,GSM, CDMA, LTE, HSPA+, or other communication typically used by awireless carrier to communicate with a mobile device such as a telephoneor tablet computing device. As discussed herein, in one exampleembodiment, the interface component 242 may be provided to facilitatecommunication between the control panel 200 and a network operationscenter (e.g., NOC 120 of FIG. 1).

In still another embodiment, the communication interface 232 may includeother components. For instance, an example control panel 200 may be usedto send and/or receive communications over a wireless protocol such asWiFi (i.e., IEEE 802.11), Bluetooth, or some other protocol. Moreover,according to some embodiments as disclosed herein, the wirelesscomponent 240 may be configured to allow the control panel 200 tofunction as a wireless access point.

According to some embodiments, the control panel 200 may further includeone or more input/output devices 230. In FIG. 2, the input/outputdevices 230 may communicate with one or more processors 228 using thecommunication bus 238. Any suitable type of input/output device may beprovided. For instance, a control panel 200 may include buttons,keypads, or the like through which input is received from a user. Adisplay 244 may also be provided and used as an output to displayinformation to a user. In some embodiments, the display 244 may also actas an input. For instance, the display 244 may be a touch-sensitivedisplay allowing a user to touch the display 244 to make a selection, toprovide input through a gesture, or to otherwise provide input. Stillother types of input or output devices may include a camera 246, one ormore sensors 248 (e.g., a microphone, infrared sensor, etc.), audiooutput devices such as a speaker 250, ports, or other elements or somecombination thereof. The illustrated input/output devices 230 of acontrol panel 200 are merely illustrative. In other embodiments, forinstance, trackball, mouse, biometric reader (e.g., iris scanner,fingerprint reader, etc.), GPS device, or other component, or somecombination of the foregoing, may be included.

The control panel 200 may also include memory 234 and mass storage 236.In general, the memory 234 may include one or more of persistent andnon-persistent storage, and in the illustrated embodiment the memory 234is shown as including random access memory 252 and read only memory 254.Other types of memory or storage may also be included.

The mass storage 236 may generally be comprised of persistent storage ina number of different forms. Such forms may include a hard drive,flash-based storage, optical storage devices, magnetic storage devices,or other forms which are either permanently or removably coupled to thecontrol panel 200. In some embodiments, an operating system 256 definingthe general operating functions of the control panel 200, and which isexecuted by the processors 228 may be stored in the mass storage 236.Other components stored in the mass storage 236 may include drivers 258(e.g., to facilitate communication between the processors 228 and theinput/output devices 230 and/or components of the communicationinterface 232), a browser 260 (e.g., to access or display informationobtained over a network, including mark-up pages and information), andapplication programs.

Application programs may generally include any program or applicationthat may be used in the operation of the control panel 200. Examples ofapplication programs may include applications specifically designed foruse with a security and/or automation system (e.g., automationapplication 262), or more general use applications. Examples of moregeneral use applications can include word processing applications,spreadsheet applications, games, calendaring applications, weatherforecast applications, sports scores applications, and otherapplications.

As shown in FIG. 2, in at least one embodiment, the automationapplication 262 may include modules or components capable of being usedby the control panel 200 in connection with a security or automationsystem. For instance, the automation application 262 may include acommunication module 264. Such a communication module 264 may generallybe used to control how one or more communication systems of a residenceor commercial building operate. As an example, an intercom system may beprovided at an entry to the building, and the communication module 264may monitor its use and potentially be used in passing communications(e.g., using a speaker or sending communications to a remote device).The communication module 264 may similarly be configured to facilitatevisual communications (e.g., using one or more cameras and/or visualdisplay devices). Moreover, the communication module 264 may be used todetermine when to communicate at all.

The illustrative automation application 262 is also shown as includingan optional entertainment module 266, HVAC module 268, and lightingmodule 270. The entertainment module 266 may generally be used tomonitor and/or control entertainment-related devices and functions of alocation. For instance, the channel or volume of a television may bemonitored and potentially changed using the control panel 200. The HVACmodule 268 may generally be used to monitor or control heating or airconditioning components. For instance, if the temperature in a locationis too high or low, a thermostat may be controlled by the HVAC module268 to obtain a more comfortable temperature. Similarly, the lightingmodule 270 may monitor, control or otherwise interface with lightingcomponents including switches, lighting fixtures, and the like. In someembodiments, such as where a light is provided at an entry way, thelighting module 270 may interface with sensors used to detect thepresence of a person (e.g., a motion sensing light). The lighting module268 may also be used to perform other functions (e.g., automaticallyturn on a light in response to a trigger event).

The modules 272, 274 may provide additional, and potentially similarfunctions. For instance, the security module 274 may be used tointerface with security-based automation components, such as sensors(e.g., motion sensors, magnetic sensors, intrusion sensors, vibrationsensors, infrared sensors, ultrasonic detectors, microwave detectors,contact sensors, photoelectric beam detectors, smoke detectors,temperature sensors, carbon monoxide detectors, etc.). When an event isdetected, the security module 274 may determine how the control panel200 should respond to the event.

The reporting module 272 may have another function. For instance, inresponse to some events, it may be desirable to provide information to aremote or other third party. As an example, a NOC may be sentinformation about an event to allow the NOC to respond to the event. Insome embodiments, the reporting module 272 may therefore collectinformation from one or more other modules 264-274 and prepare a reporton events, the status of automation components, or the like. Such areport may be prepared periodically or in response to a particularevent. In one embodiment, an event may trigger a report by the reportingmodule 272, which can then use the communication interface 232 to sendthe report to a NOC or other location.

The reporting module 272 may also be used for other functions. Asdiscussed herein, a control panel 200 may also receive information fromone or more sources. Such sources may include automation systemcomponents, and the reporting module 272 may collect, store, andpotentially report on received information. The reporting module 272 mayalso receive information from a NOC or other similar location or serviceprovider. As an example, a NOC may send information requesting that thecontrol panel 200 take a particular action (e.g., turn on an alarm). Thereporting module 272 may receive the information and then distribute theinformation to an appropriate module (e.g., security module 274) orautomation component. In still another embodiment, information that isreceived may be displayed or otherwise output using the input/outputdevices 230.

In accordance with at least some embodiments of the present disclosure,the reporting module 272 may be used to monitor events and reportinformation specific to a dealer or provider associated with the controlpanel 200. For instance, a particular service provider (i.e., a dealer),may provide the control panel 200 to a customer. The dealer may havespecific protocols for how it wishes to handle certain events detectedby the control panel 200 and the associated automation system. Thereporting module 200 may be used to provide information on thosespecific protocols to the customer. As an example, if communication islost with a particular sensor, the reporting module may determine thatthe dealer's preferred course of action is to notify the NOC of the lostcommunication, and then allow the dealer to contact the customer toset-up a service call and check on the sensor. In response, thereporting module may therefore direct the communication interface 232 tocontact the NOC and provide information about the lost communication.The reporting module 272 may further communicate with the display 244 toupdate the customer on the status. The reported information displayed onthe display 244 may indicate not only that communication was lost, butalso that the NOC or dealer was notified. Still additional informationmay include a notice that the dealer will contact the customer to set-upa service call.

The reporting module 272 may report any number of other types ofinformation, and the above example is merely illustrative. In otherembodiments, for instance, the information may indicate that thecustomer should take some course of action, that the dealer will takesome action, or that a third party will take some action. Furtherinformation available through the reporting module 272 may thereforerelate to follow-up actions to be taken in response to an event, whichactions may even be out-of-band relative to the control panel 200.Moreover, the reporting module 272 may obtain such information from alocal store of information (e.g., in storage 236 or memory 234) or froman external source (e.g., a NOC, a remote data store, etc.).

The modules shown in FIG. 2 as part of the automation application 262are purely provided to illustrate the variety of different types ofmodules that may be included, and are not intended to be an exclusivelist. In other embodiments, for instance, additional modules may includea sprinkler system module (e.g., to verify water flow rates at one ormore locations, turn sprinklers on or off, etc.), a telephone module(e.g., to interface with a telephone system and potentially runtelephone calls through the control panel, to forward calls, etc.), andthe like. Another example module could include a remote access module.Such a module could, for instance, enable the control panel 200 to beaccessed using remote devices (e.g., devices 124, 126 of FIG. 1), and topotentially have communications relayed through the control panel 200either from or to the remote devices 124, 126. Thus, a user of a remotedevice could potentially set or view communications, door cameras,entertainment, lighting, security, HVAC, sprinkler, telephone, or othersettings remotely, or even receive or otherwise monitor audio or videofeeds from a remote location. Of course, the automation application 262may also include additional or other modules or components, includingauthentication, settings, preferences, emergency override, updating, andother modules.

Turning now to FIG. 3, an example method 300 for responding to events isillustrated. The particular method 300 illustrated in FIG. 3 may allow aresponse to a detected event to include dealer-specific proceduresrelated to the event. Such procedures may be reported or otherwisecommunicated to a user of an automation system. One or more acts orsteps of method 300 may be performed by or operate in conjunction withcontrol panel 200 described above in reference to FIG. 2. Consequently,the same control panel or other device may be used in connection withany of multiple dealers to not only take actions in response to eventsas directed by a dealer, but also to notify the customer of the in-bandor out-of-band follow-up procedures recommended by a particular dealer.

More particularly, the method 300 of FIG. 3 includes detecting anautomation system event 302. As discussed herein, any number ofdifferent types of events may be detected. For instance, in anautomation system that includes a security system, an alarm, falsealarm, or other event may be detected. An automation component may alsobe determined to have low power (e.g., a low battery), or may drop outof communication with a control panel. Of course, other events may alsobe detected (e.g., a water leak in a sprinkler system, a light on whenno one is present, etc.).

Regardless of the particular type of event, a request may be prepared toobtain procedures related to the event (act 304). The request need nothave any particular form, and indeed may take the form of anotification. For instance, the request prepared in act 304 may includea notification of the detected event, and the recipient of thenotification may treat the notification as a request for information,including dealer-specific procedures as discussed herein.

Various types of procedures may be obtained. For instance, proceduresmay include steps to be taken by an automation system to respond to anevent. As an example, an alarm may sound or be turned off, a system maybe armed or disarmed, a valve may be turned on or off, or the like.Procedures may also include actions to be taken by a third party. Acentral monitoring station (e.g., a NOC, such as NOC 120 of FIG. 1) maytake some action in response to an event (e.g., initiating communicationwith the police or security, contacting an owner, etc.). In otherembodiments, procedures may relate to follow-up procedures to be takenin response to a certain type of event.

In the embodiment shown in FIG. 3, the method may be performed at leastpartially by a control panel. The control panel (e.g., control panel200) of a home automation system may request procedures related to theevent in act 304 by, for instance, querying a local database. In otherembodiments, such as that shown in FIG. 3, the control panel may makethe request by sending it to an external source such as a NOC. The NOCmay receive the request in act 306. Optionally, the request may includeinformation about the event detected in act 302. For instance, thecontrol panel may send a request or notification in act 304 thatidentifies the type of event detected, or the conditions present thatmay lead the NOC to determine an event has taken place. Using theinformation about the event, the NOC may identify procedures for theevent, which procedures can be dealer-specific (act 308). As discussedherein, such procedures can include various different types ofprocedures, including procedures to be implemented by the NOC, by thecontrol panel, by an automation system, by a third party, etc. If theNOC is to take or initiate action, the NOC may implement a response tothe event in act 310. Additionally, information to be communicated tothe customer, which information can be dealer-specific, may be sent inact 312 and received by the control panel in act 314.

Upon receipt of the dealer-specific procedures for the event in act 314,the control panel may optionally implement some response to the event inact 316. Such a response may include, for instance, sounding an alarm,turning on/off a light, resetting a system, or taking other action. Insome embodiments, the control panel may also communicate dealer-specificprocedures to the user (act 318). Communicating the dealer-specificprocedures in act 318 may also occur as part of act 316. Communicationof the dealer-specific procedures may occur in a number of differentmanners. For instance, the control panel may display text to indicatewhat action was taken by the NOC, control panel, or other device orsystem in response to the event. Such responses may be in-band orout-of-band. In still other embodiments, the communication ofdealer-specific procedures in act 318 may indicate what actions will ormay be taken in the future, or even that no action will be taken. Inanother embodiment, communication of dealer-specific procedures in act318 may include providing information to display to the user, theinformation requesting action by the user. The actions to be taken bythe user may also be in-band or out-of-band. An in-band response may,for instance, ask a user to press a button, click a link, or the like.Implementing the response in act 316 may be fully automated. In at leastone embodiment, where information is displayed, act 316 may be automatedto display information, and then may also include other automatedactions in response to a user providing in-band input at the controlpanel.

As an illustration, the method 300 may be used to detect an event suchas an alarm; however, it may be determined that the alarm was ofsufficiently short duration to be considered a false alarm. The controlpanel may prepare a request or notification of the event in act 304 andsend it to the NOC. Upon receipt of the request/notification in act 306,the NOC may identify specific procedures the dealer has for respondingto the event (act 308). For instance, because it is likely a falsealarm, the dealer-specific procedures may indicate that no call to thepolice or security is to be made, but should be treated as if no alarmhad sounded. Implementing a response in acts 310 and 316 may thereforeinclude taking no action. Additionally, however, the dealer maydetermine it is beneficial to follow-up with a home or business owner inthe event of a false alarm. The identified procedures 308 may,therefore, also indicate that the dealer's procedure is to call theowner within twenty minutes to follow-up and make sure the alarm wasindeed a false alarm.

The follow-up procedures may then be sent in act 312 to the controlpanel. Upon receipt of the follow-up procedure in act 314, the controlpanel may display information indicating the follow-up procedure of thedealer. Thus, the control panel may display a notice to the effect of “Afalse alarm was detected. We will call you shortly to check-in on you.”Of course, in addition to, or instead of, communicating the proceduresusing a display of the control panel, the communication may occur inother manners. For instance, the control panel may include a speaker foraudibly presenting the follow-up procedures of the dealer. In otherembodiments, an email, text message, or phone call may be made to aphone or other electronic device. Such a call or message may be made bythe control panel, or even by the NOC. Indeed, while FIG. 3 illustratesvarious acts as occurring at either a control panel or a NOC, any or allacts may be shifted to different locations or systems. Thus, the method300 may be fully performed in the control panel, or fully performed bythe NOC. In other embodiments, different acts 302-320 may be shiftedbetween the NOC and control panel, or even to third parties.

In response to an event, the method 300 may also include an act offacilitating implementation of dealer-specific procedures for an event(act 320). Such an act 320 may take any number of forms. By way ofexample, a dealer-specific response to an event detected by anautomation system may call for follow-up in the form of a service call.Facilitating such a dealer-specific procedure in act 320 may thereforealso include facilitating scheduling of the service call. Whereimplemented by a control panel, the control panel may display availabledates/times for a service call and, upon selection by the user,communicate the information to the NOC for scheduling. The control panelcould additionally, or alternatively, include a call device to placeoutgoing calls, so that the user can make a call directly through thecontrol panel to schedule the service call. Optionally, such schedulingis automated, but may also be initiated by the user.

To implement the method 300 of FIG. 3, a NOC, control panel, data store,or other device may include information that describes potential eventsand the procedures associated with such events. In some embodiments, theinformation may be updated to change procedures, add new procedures, oreven add information for different dealers. FIG. 4 illustrates anexample method 400 for updating information on a dealer's specificfollow-up or other procedures.

In the particular method 400 illustrated in FIG. 4, an act 402 may beincluded to provide access to a procedure description system. Suchaccess may be provided to a dealer, an administrator of the proceduredescription system, or another entity. In some embodiments, providingaccess in act 402 may include acts such as such as making the proceduredescription system available online or offline, using login or othersimilar credentials to authenticate a user of the system, or other acts,or some combination thereof. The procedure description system may behosted or available through any number of different devices or systems,including a NOC (e.g., NOC 120 of FIG. 1), remote data store (e.g., datastore 127 of FIG. 1), server, or the like.

Upon providing or granting access to the procedure description system inact 402, the identity of a specific dealer can be identified in act 404.Where, for instance, a dealer is granted access to the proceduredescription system, the particular login or other credentials used foraccess may be used to also identify the dealer. Where an administratorof the procedure description system accesses the system, theadministrator may specify a new or existing dealer in act 404. Followingidentification of the specific dealer in act 404, a custom procedure foran automation system event may be registered in step 406. The procedureregistered may be specific to the identified dealer, thereby allowing aspecific procedure to be followed, communicated, or made available to acustomer (e.g., using the method 300 of FIG. 3).

In some embodiments, different acts may be taken to register a customprocedure for an automation system event in step 406. For instance, anidentification of a type of event may be received in act 408. In effect,the act 408 may be used to determine what event type should beassociated with a procedure. Thus, a low battery event, intruder alertevent, false alarm event, water leak event, or other event may beidentified. Such an event may be pre-existing and selected from a listof available events, or may be a new type of event first identified inact 408.

The step 406 for registering a custom procedure for an automation systemevent may also include receiving custom procedures for the event (act410). As discussed herein, the procedures may relate to actions to beautomatically taken by a control panel, NOC, or other device or systemas an in-band response. Still other procedures may be follow-upprocedures that the specific dealer would like to have followed. Suchprocedures may include procedures to be taken by the dealer, the NOC, oreven the user of the automation system.

Optionally, automation options may also be provided for an event (act412). As discussed herein, for instance, an automation option may bespecified to allow automated scheduling of a service call, audio, videoor text communication, or the like. More particularly, a specific dealermay, in one embodiment, want to allow a user to use a control panel ofan automation system to schedule a service call and/or to communicatewith a central service center when a particular event is identified. Anycustom procedures and/or automation options may then be stored in act414, and be identified as specific to the dealer identified in act 404.

Turning now to FIG. 5, a table 500 is illustrated to shown an example ofa data store that may include information registered for use withautomation systems sold or administered by a specific dealer. In thetable 500, various events are identified in columns 502 and 504. Column502 may, for instance, provide an identification code or numberassociated with an event while column 504 may describe the event. Eachof various dealers may register particular types of procedures, options,and features to be associated with any or all of the events in columns502 and 504.

In the particular embodiment illustrated in FIG. 5, the table identifiestwo dealers 506 a, 506 b, although any number of dealers may beincluded. As further shown in FIG. 5, each dealer may specify one ormore follow-up procedures (column 508) that may be communicated to auser upon occurrence of the corresponding event (column 502). The firstdealer 506 a may, for instance, have registered different follow-upprocedures than the second dealer 506 b. In this particular embodiment,for instance, when an entry alarm event occurs, the first dealer 506 amay have a procedure for calling the customer within 2 minutes tofollow-up on the event. In contrast, the standard procedure for thesecond dealer 506 b may be to have the customer call service. Asdiscussed above with respect to at least FIG. 3, these procedures mayalso be communicated to the customer. Accordingly, when an entry alarmoccurs, a customer of the first dealer 506 a may receive a text message,email, or control panel audio or text message saying something to theeffect of: “A breach of your security has been detected and the policehave been notified. We will also call you within 2 minutes to see if youneed additional assistance.” In contrast, a similar message for thecustomer of the second dealer 506 b may say “A breach of your securityhas been detected and the police have been notified. Please contactservice at 1-888-555-1212 if you need additional assistance.” Notably,in each case, the control panel, NOC or other component of an automationsystem may take other actions (e.g., call the police) in addition to, orinstead of, notifying the customer of follow-up procedures. Adescription of what actions are taken actions may also be stored in thetable 500, but may instead be stored in a separate data store orlocation.

The table 500 illustrates various types of follow-up procedures that maybe specific to a particular dealer; however, such procedures are merelyillustrative. In this particular embodiment, follow-up procedures mayinclude follow-up calls that a dealer will make, or have a third partymake, to the customer. Optionally, the call or message can be specifiedwith a period of time (e.g., within 2 minutes, 10 minutes, 20 minutes, 2hours, 24 hours, etc.). Still other procedures may be taken by thedealer or a third party, such as sending of email, text messages, orother communications. In another embodiment, a follow-up procedure mayindicate that a dealer will take action such as performing a servicecall. For a low battery event, for instance, the second dealer 506 bwill replace the battery, and will call to set-up the service call to doso. Of course, these procedures may be communicated to the customer. Incontrast, for the same type of event, the first dealer 506 a may nothave any follow-up action to take, but may instead indicate that thecustomer is expected to change the battery. The customer may thus benotified that he or she is expected to make the change. Still otherfollow-up procedures, such as requesting the customer to contact aservice center, may be specified for communication to the customer.

As further reflected in table 500, a dealer may also enable optionalfunctions of a control panel in response to an event. For instance, FIG.5 illustrates a control panel functions column 510. Different optionsthat are listed may correspond to different control panel features thatmay be selectively enabled in response to an event. For instance, inresponse to an event (e.g., alarm, false alarm, etc.), the control panelmay be provided with an option to automatically call a service centerthrough the control panel (i.e., “Call Service”) option. Other optionsmay allow for direct calling of emergency services (i.e., “911Autodial”). Still other options may include an option to display certaininstructions (i.e., “Display Instructions”), which may includeinstructions for replacing a battery in a sensor, resetting a system orcomponent, or any other instructions for actions to be taken by acustomer or user of an automation system. Other options may include anonline scheduling option that can allow scheduling of a service calldirectly through the control panel. In some embodiments, the sameoptions available through a control panel may be available through othersources as well (e.g., a computer, a control panel simulator app on asmart phone or tablet, etc.).

The table 500 of FIG. 5 is intended to be illustrative in all regards,and may have additional or other features, components, or arrangements.For instance, while events may be common to multiple dealers, eachdealer may specify different events, such that a separate table 500 maybe provided for each dealer, and a collection of tables used to initiateresponses, provide information on follow-up procedures, implementevent-specific control panel functions, and the like. Further, while theprocedures and functions are illustrated in a basic form, they may bemore complex. For instance, procedures and/or functions for an event mayinclude functions or logic (e.g., Boolean logic). Thus, how a controlpanel, NOC, or other system or component responds or acts may vary incomplexity according to not only the events that occur, but on how thoseresponses are described or scripted.

As described herein, the table 500 may generally represent a data storethat can be used by a NOC, central service center, or other location torespond to events and provide a customer with specific information aboutfollow-up and other procedures for the customer's dealer or serviceprovider. In some embodiments, the dealer itself may provide such aservice, and may thus use a table 500 including only its own proceduresand protocols. In other embodiments, however, a NOC may be used bymultiple, different dealers. Where multiple dealers are used, anidentification of a control panel communicating with the NOC maypotentially be associated with a particular dealer. Consequently, whenthe control panel and NOC communicate, the control panel identificationmay be used to identify the corresponding dealer, and thus thecorresponding protocols and functions to be used and communicated.

Of course, as described herein, a NOC or other external resource may notbe used, and a control panel itself may access a remote or local copy ofthe table 500 or another suitable data store. In one embodiment, uponchanging, creating, deleting, or otherwise modifying procedures for aspecific dealer, a central location may push an update to a controlpanel. Such update may include only information for the specific dealer;however, in other embodiments the update may include information formultiple dealers.

To provide a more complete understanding of some embodiments in whichaspects of the present disclosure may be used, reference is now made toFIGS. 6-14 which illustrate an example control panel 600. Theillustrated control panel 600 may generally represent an example of acontrol panel that may be used in connection with systems, methods, anddevices of the present disclosure. For example, control panel 600 mayinclude one or more aspects of control panel 200 described above inreference to FIG. 2. In some embodiments, the control panel 600 maytherefore be used to access or receive dealer-specific protocols, and tocommunicate those protocols to a user. In FIG. 6, for instance, thecontrol panel 600 is shown as including a display 602, speaker 604,microphone 606, and input devices 608, 610. The display 602 may providetext, images, video, and other information that may be visually depictedto the customer. The speaker 604 may provide information to be audiblyconveyed to the customer. Examples of such information may includealarms or alerts; however, other information may also be provided. Forinstance, the control panel 600 may be used to receive audible messagesfrom a service center, and potentially to engage in two-waycommunication. Thus, the microphone 606 may receive audio informationand pass it to a representative at a service center, a caller on a phoneline, a person in another room through an intercom, or the like.

The illustrated input devices 608, 610 generally represent any ofvarious other types of inputs that may be used to interact with thecontrol panel 600. Input device 608 may, for instance, be a button usedto initiate an emergency call. Such a call may be placed to a responsecenter for the dealer of the control panel, or to a local police,security, fire department, or other emergency response location. Theinput device 610 is illustrated as a “home” button. In some embodiments,the display 602 may include different interfaces or screens, and thehome option may be used to return to a so-called home or initial screen.In other embodiments, other types of input/output devices may also beprovided as discussed herein. Examples of other input devices mayinclude keypads, sensors, and ports. In some embodiments, the display602 may also act as an input device, such as where the display 602 istouch-sensitive.

As discussed herein, the control panel 600 may interface with, or bepart of, an automation system that includes one or more automationcomponents. Examples of different types of automaton components aredescribed herein, and can include security components, lightingcomponents, HVAC components, and the like. Optionally, the control panel600 monitors such automation components and detects events that occur.

According to at least some embodiments, the control panel 600 maycommunicate with one or more automation components of a security system(e.g., security system 114 of FIG. 1). FIG. 7 illustrates the controlpanel 600 in an example embodiment following detection of an event by asecurity system component. In this particular embodiment, the componentmay have detected a breach at a particular location (e.g., a front doorto a building). In response, the control panel may use the display 602to notify a user of the event. Optionally, the speaker 604 may be usedto sound an alarm, or other actions may be taken.

In accordance with one embodiment, the control panel may also be used todetermine follow-up or other procedures specific to the dealer providingthe control panel 600, and to communicate such information available tothe customer. As an example, the control panel 600 may automaticallyaccess a data store and identify dealer-specific procedures and/orcommunicate with a NOC to obtain such procedures. In response, theprocedures may be communicated to the customer. FIG. 8, for instance,illustrates the control panel 600 after obtaining dealer-specificprocedures in accordance with one embodiment. In this particularembodiment, a response may be initiated (e.g., calling the police), andpotentially communicated by displaying information on the display 602.The dealer may also take other actions to follow-up on the event. Forinstance, the dealer may have a procedure to have a servicerepresentative call to make sure everything is okay with the customer.In FIG. 8, the display 602 also indicates that a call will be made tothe customer to check on them. While such information is shown on thedisplay 602, it may also be provided in additional or other manners,including through the speaker 604. The control panel 600 and/or a NOC orother component may also send information to other devices, including toelectronic devices such as computing devices, tablet devices, and mobilephones.

In addition to notifying the customer of follow-up procedures that willbe taken by the dealer, and/or what responses have already been taken,the control panel 600 may also facilitate other actions to be taken bythe customer. FIG. 9, for instance, illustrates an embodiment in whichthe display 602 is used to instruct a customer to press the input device608 if additional assistance is needed. In this particular embodiment,pressing the input device 608 may direct a customer to the dealer'semergency response team. Such an option may be the standard use of theinput device 608, and the information on the display 602 may includestandard instructions for how to use the input device 608. In otherembodiments however, the function of the input device 608 may be changedor overridden. As an example, the input device 608 could normallyinitiate communication with a dealer's emergency response or serviceteam, but upon an event such as a smoke alarm, the emergency button orother input device 608 may instead route contact to a fire department orother local emergency center.

FIGS. 10-14 illustrate still additional embodiments of the control panel600 in additional examples that may further illustrate some aspects ofthe present disclosure. In particular, the control panel 600 of FIG. 10may detect a problem with an automation component, or communication withan automation component. The problem may be logged as an event and usedto identify specific procedures the dealer may have for responding tothe event. Optionally, the event itself may also be reported using thecontrol panel. FIG. 10, for instance, displays information about theevent on the display device 602.

Upon receipt of dealer-specific procedures from a remote (e.g., a NOC)or local (e.g., internal storage) source, the dealer-specific procedurescan be identified and communicated to the user. Thus, in FIG. 11, thecontrol panel 600 may access or receive information indicating that thedealer's standard procedures for a loss of communication is to schedulea service call where the dealer can check it out. Additional proceduresmay indicate that the dealer will initiate a phone call or othercommunication to schedule the call. These procedures may then becommunicated to the customer (e.g., using the display device 602).

Optionally, additional functionality may be enabled or facilitated byaccessing dealer-specific information. FIG. 12, for instance,illustrates an example in which the control panel 602 may be used toallow the customer to schedule the service call. Such functionality isoptionally embedded in the operating system or application programs ofthe control panel 600. Upon identifying the dealer's procedure toperform a service call to remedy an event, the functionality may beenabled. In other embodiments, the option may always be enabled, and thecontrol panel 600 may simply direct the user to the appropriateinterface to facilitate its use.

In the particular embodiment illustrated in FIG. 12, the control panel600 may display information to allow a user to schedule a service callusing either of two methods. For instance, a user may select a “call”option to initiate a voice and/or video call with a servicerepresentative. The display 602 may include touch screen capabilities toallow the user to select a corresponding “call” button to initiate thecall. Alternatively, the user may schedule the service call through thecontrol panel 600 (or smart phone application, browser, etc.), byselecting a “schedule” button.

FIGS. 12 and 13 illustrate one manner in which the scheduling option maybe used. As an example, upon selecting an option to schedule a servicecall through the control panel 600, the display 602 may present acalendar or other similar option showing days available to schedule thecall. Optionally, the control panel 600 may communicate with a servicecenter, NOC, or other location to obtain information on which days areavailable for the service call. Upon selection of a day (e.g., bytouching the day on the touch screen display 602 of FIG. 13), theservice center, NOC, or other location can be notified and the servicecall scheduled. In some embodiments, however, a user may be able toschedule a time during the day for the service call to occur. FIG. 14,for instance, illustrates an example in which the user has selectedApril 15th for a service call. The user can then select any of theavailable times, and then press the “Submit” option to schedule theservice call. Optionally, once scheduled, the control panel 600, NOC, aservice center, or other component or system may send a text message,calendar item, email, or other notification to the customer.

While FIGS. 6-14 illustrate example embodiments in which a control panel600 may be used to carry out particular acts, or communication certaininformation, such embodiments are merely illustrative. As an example,dealer specific information may be communicated to a customer withoutusing the control panel. For instance, a control panel may be used tosense an event in the automation system and communicate the informationto a NOC or other location. The NOC can determine what dealer providedthe control panel and what specific procedures, including follow-upprocedures, the dealer has registered. The NOC may send a text, email,or other message to an electronic device to provide information thatcould alternatively, or additionally, be sent to the control panel.

In reference now to FIG. 15, a method 1500 is shown for providing anautomation system user with one or more procedures in response to anevent of the automation system, as described herein. The method 1500 mayinclude one or more aspects of method 300 described above in referenceto FIG. 3, and may be implemented by one or more of an NOC 120 of FIG.1, a control panel, such as control panels 200 and/or 600 of FIGS. 2 and6-14, any other automation system components, and/or one or more userdevices 124, 126. Furthermore, method 1500 may utilize informationrelated to one or more procedures, for example from table 500 describedin reference to FIG. 5, one or more local data stores, and/or one ormore remote data stores (e.g. data store 127). The method 1500 may alsobe implemented with one or more aspects of methods 300 and/or 400 ofFIGS. 3 and/or 4.

In one aspect, method 1500 may include detecting an event in anautomation system at act 1502. The automation system may include one ormore automation components that are communicatively linked to a controlpanel. The one or more automation components may detect an event, suchas a door opening, the presence of smoke, etc., and may communicate anindication of the event to the control panel, which may in turn in someembodiments, communicate the indication to the NOC.

At act 1504, one or more procedures specific to the event and a dealerassociated with the automation system may be automatically accessed, forexample from a local or remote data store, such as from table 500 ofFIG. 5.

At act 1506, at least a portion of the one or more procedures specificto the event and the dealer associated with the automation system may beexecuted, as described in detail above. Executing the one or moreprocedures, for example, may include sending and/or displayinginformation on a control panel of the automation system, calling anemergency responder (e.g., police, fire, etc.), etc.

In reference now to FIG. 16, a method 1600 is shown for providingregistration of custom procedures in response to one or more eventsdetected in an automation system, as described herein. The method 1600may include one or more aspects of method 400 described above inreference to FIG. 4, and may be implemented by one or more of an NOC 120of FIG. 1, a control panel, such as control panels 200 and/or 600 ofFIGS. 2 and 6-14, any other automation system components, and/or one ormore user devices 124, 126. Furthermore, method 1600 may utilize and/oraccess information related to one or more procedures, for example fromtable 500 described in reference to FIG. 5, one or more local datastores, and/or one or more remote data stores (e.g. data store 127). Themethod 1600 may also be implemented with one or more aspects of methods300, 400, and/or 1500 of FIGS. 3, 4, and/or 15.

In one aspect, method 1600 may include accessing a procedure descriptionsystem at act 1602. The method 1600 may further include identifying aspecific dealer associated with the automation system at act 1604. Atact 1606, method 1600 may also include registering in the proceduredescription system a custom procedure, the custom procedure beingassociated with an automation system event of the automation system andthe specific dealer associated with the automation system. In somecases, acts 1602-1606 may be performed in conjunction with table 500described above in reference to FIG. 5. For example, table 500 may beaccessed at act 1602. Next a dealer associated with the automationsystem may be identified at act 1604 and located in the table via thedealer field 506. Registering the procedure at act 1606 may includecreating or modifying an existing row in table 500, such that the customproducer is entered in the follow-up and/or control panel functionsfields 508, 510, associated with an event via an event ID 502 and/or anevent description 504. In this way, custom procedures may be entered andstored in a data store, such as table 500 of FIG. 5, to allow futureevents occurring at the automation system to prompt action according tothe custom procedures.

Embodiments of the present disclosure may comprise or utilize a specialpurpose or general-purpose computer including computer hardware, suchas, for example, one or more processors and system memory. Embodimentswithin the scope of the present disclosure also include physical andother non-transitory computer-readable media for carrying or storingcomputer-executable instructions and/or data structures. Suchcomputer-readable media can be any available media that can be accessedby a general purpose or special purpose computer system.Computer-readable media that store computer-executable instructions arecomputer storage media. Computer-readable media that carrycomputer-executable instructions are transmission media. Thus, by way ofexample, and not limitation, embodiments of the disclosure can compriseat least two distinctly different kinds of computer-readable media,including at least computer storage media and/or transmission media.Computer-readable media that includes computer-executable instructionsmay also be referred to as a computer program product.

Examples of computer storage media include RAM, ROM, EEPROM, CD-ROM orother optical disk storage, magnetic disk storage or other magneticstorage devices, flash-based storage, solid-state storage, or any otherphysical, non-transmission medium which can be used to store desiredprogram code means in the form of computer-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer.

When information is transferred or provided over a communication networkor another communications connection (either hardwired, wireless, or acombination of hardwired or wireless) to a computing device, thecomputing device properly views the connection as a transmission medium.A “communication network” may generally be defined as one or more datalinks that enable the transport of electronic data between computersystems and/or modules, engines, and/or other electronic devices, andtransmissions media can include a communication network and/or datalinks, carrier waves, wireless signals, and the like, which can be usedto carry desired program or template code means or instructions in theform of computer-executable instructions or data structures within, toor from a communication network. Combinations of storage media andtransmission media should also be included within the scope ofcomputer-readable media.

Further, upon reaching various computer system components, program codemeans in the form of computer-executable instructions or data structurescan be transferred automatically from transmission media to storagemedia (or vice versa). For example, computer-executable instructions ordata structures received over a network or data link can be buffered inRAM within a network interface module (e.g., a “NIC”), and theneventually transferred to computer system RAM and/or to less volatilecomputer storage media at a computer system. Thus, it should beunderstood that computer storage media can be included in computersystem components that also (or even primarily) utilize transmissionmedia.

Computer-executable instructions comprise instructions and data which,when executed at a processor, cause a general purpose computer,dedicated or special purpose computer (e.g., an automation systemcontrol panel), or special purpose processing device to perform acertain function or group of functions. The computer executableinstructions may be, for example, binaries, intermediate formatinstructions such as assembly language, or even source code. Althoughthe subject matter has been described in language specific to structuralfeatures and/or methodological acts, it is to be understood that thesubject matter defined in the appended claims is not necessarily limitedto the described features or acts described above, nor performance ofthe described acts or steps by the components described above. Rather,the described features and acts are disclosed as example forms ofimplementing the claims.

Those skilled in the art will appreciate that the embodiments may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, programmablelogic machines, multi-processor systems, microprocessor-based orprogrammable consumer electronics, network PCs, tablet computingdevices, minicomputers, automation system control panels, networkoperations centers, mainframe computers, mobile telephones, PDAs,pagers, routers, switches, and the like.

Embodiments may also be practiced in distributed system environmentswhere local and remote computer systems, which are linked (either byhardwired data links, wireless data links, or by a combination ofhardwired and wireless data links) through a network, both performtasks. In a distributed computing environment, program modules may belocated in both local and remote memory storage devices.

Those skilled in the art will also appreciate that embodiments of thepresent disclosure may be practiced in special-purpose, dedicated orother computing devices integrated within or particular to a particularresidence, business, company, government agency, or other entity, andthat such devices may operate using one or more network, wireless,hardwire, or other connections, or any combination thereof. Examples mayinclude residential or commercial buildings in connection with securityor other automation systems configured to monitor local conditions(i.e., within a specific range of the building), remote conditions(i.e., accessible regardless whether within a particular range), or somecombination thereof.

Although the foregoing description contains many specifics, these shouldnot be construed as limiting the scope of the disclosure or of any ofthe appended claims, but merely as providing information pertinent tosome specific embodiments that may fall within the scopes of thedisclosure and the appended claims. Various embodiments are described,some of which incorporate differing features. Any feature illustrated ordescribed relative to one embodiment is interchangeable and/or may beemployed in combination with features of any other embodiment herein. Inaddition, other embodiments may also be devised which lie within thescopes of the disclosure and the appended claims. The scope of thedisclosure is, therefore, indicated and limited only by the appendedclaims and their legal equivalents. All additions, deletions andmodifications to the disclosure, as disclosed herein, that fall withinthe meaning and scopes of the claims are to be embraced by the claims.

1-20. (canceled)
 21. A method for communicating dealer-specificprocedures associated with a home automation system, comprising:detecting an event associated with the home automation system, the homeautomation system comprising at least one home automation systemcomponent; identifying a dealer associated with the home automationsystem based at least in part on detecting the event associated with thehome automation system; determining at least one procedure specific tothe event and to the dealer; and implementing the at least one procedurespecific to the event and to the dealer associated with the homeautomation system.
 22. The method of claim 21, further comprising:transmitting the at least one procedure specific to the event and to thedealer associated with the home automation system to a user of the homeautomation system.
 23. The method of claim 21, wherein identifying thedealer associated with the home automation system comprises accessing aremote server to identify the dealer.
 24. The method of claim 21,further comprising: identifying a second dealer associated with the homeautomation system based at least in part on detecting the eventassociated with the home automation system, the second dealer differentthan the dealer; and determining at least one second procedure specificto the event and to the second dealer, the second procedure differentthan the at least one procedure specific to the event and to the dealer.25. The method of claim 24, further comprising: implementing the atleast one procedure specific to the event, the at least one secondprocedure specific to the event, or both based at least in part on theevent associated with the home automation system.
 26. The method ofclaim 21, further comprising: display a user interface at the homeautomation system; receive a user selection via the user interface, theuser selection associated with the at least one procedure specific tothe dealer; and communicate the user selection to the dealer.
 27. Themethod of claim 21, further comprising: implementing at least onefollow-up procedure after implementing the at least one procedurespecific to the event and to the dealer associated with the homeautomation system.
 28. The method of claim 21, further comprising:displaying the at least one procedure specific to the event at the homeautomation system.
 29. The method of claim 21, wherein the eventassociated with the home automation system comprises at least one of analarm, a false alarm, a low battery, a water leak, a communication errorassociated with one or more components of the home automation system, ora combination thereof.
 30. The method of claim 21, wherein the eventassociated with the home automation system is detected via at least oneof a motion sensor, a magnetic sensor, an intrusion sensor, a vibrationsensor, an infrared sensor, an ultrasonic detector, a microwavedetector, a contact sensor, a photoelectric beam detector, a smokedetector, a temperature sensor, a carbon monoxide detector, or acombination thereof.
 31. A method for registering dealer-specificprocedures associated with events in a home automation system,comprising: accessing a procedure description system associated with aplurality of dealers associated with home automation systems;identifying at least one dealer associated with the home automationsystem; and registering a procedure at the procedure description systemassociated with the at least one dealer, the procedure associated withan event detected via the home automation system.
 32. The method ofclaim 31, further comprising: authoring the at least one dealer toaccess the procedure description system based at least in part on acredential of the at least one dealer.
 33. The method of claim 32,wherein identifying the at least one dealer is based at least in part onthe credential of the at least one dealer.
 34. The method of claim 31,wherein registering the procedure at the procedure description systemcomprises storing the procedure at a server associated with a pluralityof home automation systems.
 35. A control panel of a home automationsystem, comprising: one or more processors; a display device; andnon-transitory computer-readable media storing computer-executableinstructions that, when executed by the one or more processors, causethe control panel to: detect an event associated with the homeautomation system, the home automation system comprising at least onehome automation system component; identify a dealer associated with thehome automation system based at least in part on detecting the eventassociated with the home automation system; determine at least oneprocedure specific to the event and to the dealer; and implement the atleast one procedure specific to the event and to the dealer associatedwith the home automation system.
 36. The control panel of the homeautomation system of claim 35, wherein the non-transitorycomputer-readable media further store computer-executable instructionsthat, when executed by the one or more processors, cause the controlpanel to: transmit the at least one procedure specific to the event andto the dealer associated with the home automation system to a user ofthe home automation system.
 37. The control panel of the home automationsystem of claim 35, wherein the non-transitory computer-readable mediafurther store computer-executable instructions that, when executed bythe one or more processors, cause the control panel to: identifying asecond dealer associated with the home automation system based at leastin part on detecting the event associated with the home automationsystem, the second dealer different than the dealer; and determining atleast one second procedure specific to the event and to the seconddealer, the second procedure different than the at least one procedurespecific to the event and to the dealer.
 38. The control panel of thehome automation system of claim 37, wherein the non-transitorycomputer-readable media further store computer-executable instructionsthat, when executed by the one or more processors, cause the controlpanel to: implement the at least one procedure specific to the event,the at least one second procedure specific to the event, or both basedat least in part on the event associated with the home automationsystem.
 39. The control panel of the home automation system of claim 35,wherein the non-transitory computer-readable media further storecomputer-executable instructions that, when executed by the one or moreprocessors, cause the control panel to: implement at least one follow-upprocedure after implementing the at least one procedure specific to theevent and to the dealer associated with the home automation system. 40.The control panel of the home automation system of claim 39, wherein theat least one follow-up procedure comprises: an in-band procedure; or anout-of-band procedure.